History | ![]() |
About settings files
FirstClass stores the information needed to connect to a server in a settings file. Settings files can also store resources used by FirstClass, such as forms, pictures, and sounds. In Windows, settings files always end in .fc.
FirstClass includes a home.fc settings file. If you downloaded FirstClass from your server and followed the instructions there, this settings file already knows your server's name.
If you just use home.fc to connect to your server, and this connection works well the first time you click Login, you will not need to configure your connection. You only need to read the information about configuring if you must change connection information for home.fc or you want to configure a connection to another server.
Your administrator may have provided you with a settings file that contains the necessary information for logging into your server. If this is the case, put this file in the FirstClass Settings folder.
Providing a shared home.fc settings file for multiuser computers
By default, all settings files created by a user are placed in the FirstClass Settings folder that is located in that user's personal user space. This includes the home.fc settings file that is automatically created when the user first runs the client.
If FirstClass is running on a computer with multiple users, the computer administrator (the person who logs into the computer as Administrator, not your FirstClass administrator) can create a home.fc settings file for use by all users of that computer.
To do this, the computer administrator must be the first to run the FirstClass client. This will place home.fc in the administrator's personal user space. The administrator saves connection information, but not a user ID or password. After home.fc has been created, the administrator can drag it into the FirstClass Settings folder that is located in the shared applications area.
This settings file will now be used by subsequent users on the computer. If a user updates home.fc, a copy containing the updates will be placed in that user's personal user area. The shared settings file won't be changed.
If you want different behaviors for the same protocol
When you configure a connection, you are updating the .fcp file that is used for all connections using this protocol (for example, all modem connections).
If you want to make a change that only applies to one settings file, and not to others that use the same .fcp file, you can create a new .fcp file. To do this, create a duplicate of the applicable .fcp file in the FirstClass FCP folder, then name the duplicate, using the extension .fcp.
Example
You have a modem connection for which you want the speaker on for some systems, but off for others. You copy MODEM.FCP and rename the duplicate QUIET.FCP to accommodate turning the speaker off. Then you can create a new settings file that uses QUIET.FCP, or just change the selection as necessary when you log in.
| ||